The requirements to be captured cover a number of areas such as;-
Functional, non-functional and legal requirements, as well as the dependencies between the item and its environment.
Safety requirements that are already known about, these cover behavior achieved by similar functions, assumptions on
behavior expected by the item and potential consequences of behavior shortfalls, including failures modes and hazards.
This task could be considered to be similar to capturing stakeholder requirements.
The scope of item development and interfaces also needs to be understood, this is determined by considering
interactions with items or elements outside the scope of the system, allocation and distribution of functions to
architecture and operating scenarios, if they impact the functionality of the item.
This can be achieved using Use Case modeling if an MBSE approach is being used, see SE Overview. This details a generic process for developing systems using model based techniques and gives an overview
of the process. The user is recommended to examine Elaborate Draft System Requirements Specification, in particular, to help
with the item definition.
For a more detailed understanding of the requirements for Item Definition the user is referred to ISO 26262
vol 3 clause 5.
|